Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
tsconfig-resolver
Advanced tools
A tool for loading the nearest tsconfig file in the same way the TypeScript compiler does. It walks up the directory tree until it finds the first matching tsconfig.json
file.
tsconfig-resolver
is designed to be used inside your node project.
First, install the plugin and it's peer dependencies:
npm install --save tsconfig-resolver
or
yarn add tsconfig-resolver
The following will load the first tsconfig.json
file working upwards from the process.cwd()
of the running node process.
import { tsconfigResolver } from 'tsconfig-resolver';
const result = tsconfigResolver();
// without type narrowing
console.log(result?.config);
// with type narrowing
if (result.exists) {
console.log(result.config);
}
Configuration options can also be passed into the export function.
import { join } from 'path';
import { CacheStrategy, tsconfigResolver } from 'tsconfig-resolver';
const result = tsconfig({
cwd: join(__dirname, 'src'),
fileName: 'tsconfig.prod.json',
cacheStrategy: CacheStrategy.Directory,
});
tsconfigResolver
import { tsconfigResolver } from 'tsconfig-resolver';
The function returns an object consisting of the following.
Property | Type | Description |
---|---|---|
config | TsConfigJson or undefined | The configuration object.
|
exists | boolean | Whether or not the configuration could be loaded.
|
reason | TsConfigErrorReason or undefined | The reason for failure.
|
path | string or undefined | The absolute path to the tsconfig.json or given filename.
|
extendedPaths | string[] or undefined | The extendedPaths array.
|
isCircular | boolean or undefined | The isCircular config flag.
|
Property | Type | Default | Description |
---|---|---|---|
cwd | string | process.cwd() | The directory to start searching from. |
searchName | string | 'tsconfig.json' | The tsconfig file name to search for. This is where the TsConfigJson configuration object will be loaded from. |
filePath | string | undefined | A direct path to the tsconfig file you would like to load. The path will be resolved relative to the current process.cwd() . If it leads to a directory then the searchName will be appended. * This also supports the npm: prefix which will find the given npm package directory, if it is installed. When provided the cacheStrategy is set to 'always' by default. |
cacheStrategy | string | 'never' | Set the caching strategy that will be used when searching for a file that's already been found. When a filePath is provided the default value becomes 'always' . |
ignoreExtends | boolean | false | When true will not automatically populate the extends argument. This is useful if all you want is the json object and not the fully resolved configuration. |
clearCache
Clears the cache.
import { clearCache, tsconfigResolver } from 'tsconfig-resolver';
const result = tsconfigResolver();
// Now clear the cache.
clearCache();
CacheStrategy
import { CacheStrategy } from 'tsconfig-resolver';
Provides the available caching strategies that can be used.
Sometimes you'll want to run this module several times during runtime but it can be slow and expensive walk up the file tree for the tsconfig value every time.
To help prevent unnecessary lookups there are custom caching strategies available.
CacheStrategy.Never
- Caching never happens and the returned value is always recalculatedCacheStrategy.Always
- The first time the tsconfigResolver
method is run it will save a cached value (by searchName
) which will be returned every time after that. This value will always be the same. This is turned on by default when a filePath
is provided.CacheStrategy.Directory
- The cache will be used when the same directory (and searchName
) is being searched.TsConfigErrorReason
import { TsConfigErrorReason } from 'tsconfig-resolver';
This provides the reason for the error in resolving the tsconfig
.
TsConfigErrorReason.NotFound
- The tsconfig
file could not be found.TsConfigErrorReason.InvalidConfig
- The file was found but the configuration was invalid.TsConfigJson
Re-exported from type-fest
.
Dive into the codebase with Gitpod.
This project uses SemVer for versioning. For the versions available, see the tags on this repository.
This project is licensed under the MIT License - see the LICENSE file for details
FAQs
Walk up the tree to resolve `tsconfig.json` configuration objects.
The npm package tsconfig-resolver receives a total of 13,076 weekly downloads. As such, tsconfig-resolver popularity was classified as popular.
We found that tsconfig-resolver demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.